IBM Token-Ring Adapter

Chapter 7. Redundant NIC

Supported Environments

Redundant NIC is currently supported on the following adapters:

• IBM PCI Token-Ring Adapter

• IBM PCI Wake on LAN Token-Ring Adapter

• IBM 16/4 Token-Ring PCI Adapter 2

• IBM 16/4 Token-Ring PCI Adapter 2 with Wake on LAN

• IBM High-Speed 100/16/4 Token-Ring PCI Adapter

The following operating environments are supported:

• Windows NT Server 3.51 and 4.0

• NetWare 4.11

Overview

The Redundant NIC function provides a high-availability solution for your Windows NT Server 3.51 and 4.0 or NetWare 4.11 server. This function maintains network connectivity in the event of an adapter- or lobe-related failure. You can assign a backup adapter to take control of the network connection if the active adapter fails.

The Redundant NIC function will initiate a failover when a cable fault or a hard error occurs on the adapter. A failover causes the driver to switch traffic from the active adapter to the backup adapter. The active and backup roles are traded between the adapters of the redundant pair.

In many cases, the failover to the backup adapter will occur seamlessly. Due to the failover latency involved in opening the backup adapter onto the ring, some protocols might require that sessions be reestablished. In either case, network connectivity is maintained and server downtime is avoided.

Benefits

The Redundant NIC function provides a high-availability solution for your Token-Ring connected servers. The goal of Redundant NIC is to maintain network connectivity in the event of an adapter- or lobe-related failure.

Example Scenarios

Managing a Redundant NIC NT Server with the Agent

During driver configuration, users can define a Redundant NIC pair. The pair consists of an active adapter and a backup adapter. The backup adapter will take over in the event of a failure on the active adapter. These failovers can occur continually as long as the backup adapter is operational. Redundant NIC is offered on Windows NT and NetWare server systems. The LAN Adapter Management Agent can be used to complement the Redundant NIC function on Windows NT.

The Agent will send a DMI indication and SNMP trap upon detecting the completion of a Redundant NIC failover. The Agent also allows a failover to be initiated via DMI or SNMP. The Agent also provides the addresses of the active and backup adapters, a running count of failovers and the status of the backup adapter. The Nways Management Applications format the contents of the failover SNMP trap into a clear message.

The combined Redundant NIC and Agent functions should be used on mission-critical servers and the Nways Management Applications should be used to monitor those servers. Redundant NIC provides the continual network connectivity necessary for the clients using the Windows NT Server. The Agent sends the failover SNMP trap to the Nways Management Application, or any other SNMP-based network management application. Once notified of the server failover, the network administrator can correct the error. For example, the error might be an accidently-disconnected cable. Once the cable has been reconnected, the network administrator can then force a failover from the management application and restore the server's original adapter configuration.

Installation and Configuration

Windows NT

Follow these instructions when setting up a Redundant NIC pair.

1. Ensure that both adapters of a redundant pair are cabled to the same network.

2. Select Control Panel > Network > Adapters and your adapter. Use the Redundant NIC tab located in Properties for the primary adapters to control your redundant pairs.

3. You must specify a Locally Administered Address (LAA) for the primary adapter. The LAA is located in the Basic tab of Properties for the primary adapter.

Redundant NIC Usage Tips

• It is strongly recommended that you specify a Ring Speed parameter of 16 Mbps or 4 Mbps instead of Automatic. This will reduce the amount of time needed to perform a failover.

• Once a redundant pair has been defined, the secondary adapter is not configurable until the redundancy has been disabled.

• Once a redundant pair has been defined, neither the primary nor the secondary adapter can be removed until the redundancy has been disabled.

• When a failover occurs, check the cabling of the failed adapter. If it has been disconnected, reconnect it as soon as possible so that it is ready to function as a backup.

• The Redundant NIC function is supported on the IBM PCI Token-Ring adapter family; the Auto LANStreamer PCI adapter is not supported.

Managing Redundant NIC

The LAN Adapter Management Agent Version 1.40 allows you to manage the Redundant NIC operation. In the event of a failover, the Agent sends an SNMP trap to notify that a failover has occurred. The user can also initiate a failover through the Agent. For more information about the Agent, see Chapter 4. "LAN Adapter Management Agent". For an example of using the Agent and Redundant NIC, see "Example Scenarios".

NetWare

The Redundant NIC function is provided in 2 pieces: RNIC.NLM and IBMTRPO.LAN. When a failover from the active to the backup adapter occurs, the only protocols that can be switched are IP and IPX. Any other protocol information that is bound to the active adapter will be lost.

Note: The only protocol information that is retained when a failover occurs is what is bound to the active adapter when the problem occurs. No conflicting protocols should be bound to the backup adapter. The only exception to this is when ROUTE.NLM is used. In that case, ROUTE.NLM should be bound to the active and backup adapters.

Failover can occur from the active to the backup adapter, and also from the backup to the active until a good connection is made. If the backup adapter is not an IBM PCI Token-Ring adapter then only one automatic failover to the backup is supported. The Redundant NIC NLM can monitor four pairs at one time.

Installation of Redundant NIC Software

Versions of IBMTRPO.LAN prior to Version 2.14 will not work with the Redundant NIC capability.

The network data rate must be set to the same value (16 Mbps or 4 Mbps) on both adapters or the Redundant NIC NLM will not allow the pair to be made. Each adapter must be plugged into the same ring on the network for the failover to be completely transparent to the clients communicating with the server.

The driver communicates adapter failures or cable disconnects to the RNIC NLM via the NESL/NEB interface. If ODINEB.NLM loads after the LAN driver, these messages are never sent to the RNIC NLM by the NESL/NEB subsystem. If the RNIC NLM does not failover after a cable disconnect or failure, verify that ODINEB.NLM is loading before the LAN driver.

If you use INETCFG.NLM to configure your system, follow the steps in "Installation Using INETCFG.NLM" instead of the following INSTALL.NLM section.

Installation Using INSTALL.NLM

1. Install the ODI33F.EXE or higher patch from Novell.

2. Install the adapters you would like to pair into a NetWare 4.11 Server.

3. Copy RNIC.NLM, TOKENTSM.NLM, and ODINEB.NLM from the \NOVELL\NETWARE directory on the driver diskette to SYS:\SYSTEM on the server.

4. LOAD INSTALL on the server and proceed to the section where you install network adapters.

5. Set up the primary adapter:

   While in the Load Software panel, you will need the following information:

   The path for the driver is A:\NOVELL\NETWARE.

   Copy the new driver (IBMTRPO.LAN) and IBMTRPO.LDI from the diskette.

   Choose protocols. In the Parameters panel, fill in a node address. Set Standby Mode to DISABLED unless using the "-backup" parameter. Set other parameters as needed.

   Save and load the driver. While it is processing, press ALT+ESC to get to the Console panel. Choose the slot of the primary adapter.

   Choose a network number to bind to.

6. Set up the secondary adapter:

   Choose to load an additional network driver.

   Do not copy the driver again.

   Select the same protocols you chose to use with the primary adapter. If you chose TCP/IP, use a temporary IP address for the secondary adapter. You must use the same Node Address. Standby Mode must be set to ENABLED. If using the "-backup" parameter then the Standby Mode will probably not exist for a non IBM PCI Token-Ring adapter. Save and load the driver.

   While it is processing, press ALT+ESC to get to the Console panel. When asked to load another frame type, answer NO.

   Choose the slot of the secondary adapter.

   Choose a temporary network number to bind to.

   Do not load an additional network driver.

7. Exit back to the Console.

8. Edit the AUTOEXEC.NCF file:

   • Before all of the LOAD statements, add LOAD ODINEB.

   • After all of the BIND statements, add LOAD RNIC PAIR -p -s and any additional parameters. See "Setting up a Redundant NIC Pair". If the secondary adapter is not an IBM PCI Token-Ring adapter then the -backup parameter must be used on the pair line. Also, since the secondary adapter probably will not support the standby keyword, the primary adapter must be loaded with the standby keyword.

   • Delete all BIND statements for the secondary adapter.

9. Restart the server in order for the changes to take effect.

Note: Double-check your AUTOEXEC.NCF every time that you use the INSTALL.NLM program. It is possible that the INSTALL.NLM will move or remove ODINEB.NLM. Make sure that it loads before the network driver (IBMTRPO.LAN) and that RNIC loads after the network driver.

Installation Using INETCFG.NLM

1. Install the ODI33F.EXE or higher patch from Novell.

2. Install the adapters you would like to pair into a NetWare 4.11 Server.

3. Copy RNIC.NLM, TOKENTSM.NLM, and ODINEB.NLM from the \NOVELL\NETWARE directory on the driver diskette to SYS:\SYSTEM on the server.

4. LOAD INETCFG on the server and proceed to the section where you add a new board.

5. Set up the primary adapter:

   While in the New Board panel, you will need the following information:

   The path for the driver is A:\NOVELL\NETWARE.

   Choose IBMTRPO from the list.

   In the Configuration Panel, name the Board, fill in the slot number, and the node. Standby Mode must be set to DISABLED unless the "-backup" parameter is specified. Set other parameters as needed.

   Save the changes.

6. Set up the secondary adapter:

   Choose IBMTRPO from the list unless a non IBM PCI Token-Ring adapter is being used as the secondary adapter. In this case, use the appropriate driver for the secondary adapter.

   In the Configuration panel, name the Board (the name must be different from that of the primary adapter), fill in the slot number, and the node (must be the same as that of the primary adapter). Standby Mode must be set to ENABLED unless the "-backup" paramter is specified. Set other parameters as needed.

   Save the changes.

7. In the Protocols section, select User-specified Protocols, create and name a temporary protocol and save that information.

8. In the Bindings section, choose binding parameters for the primary adapter as needed. Bind the User-specified Protocol that you defined in the previous step to all appropriate frame types of the secondary adapter.

   Since the User-specified Protocol that you created does not exist, no protocols will actually be bound to the secondary adapter. You might notice error messages that point this out when the server is starting up. These messages are for information only; no action is required.

9. Exit back to the Console.

10. Edit the AUTOEXEC.NCF file:

    • Before the INITSYS.NCF command, add LOAD ODINEB.

    • After the INITSYS.NCF command, add LOAD RNIC PAIR -p -s and any additional parameters. See "Setting up a Redundant NIC Pair". If the secondary adapter is not an IBM PCI Token-Ring adapter than the -backup parameter must be used on the rnic pair line. The primary adapter must also be loaded with the standby keyword.

11. Restart the server in order for the changes to take effect.

    Note: Double-check your AUTOEXEC.NCF every time you use the INETCFG.NLM program. It is possible that the INETCFG.NLM will move or remove ODINEB.NLM. Make sure that it loads before the network driver (IBMTRPO.LAN) and that RNIC loads after the network driver.

Setting up a Redundant NIC Pair

Follow these instructions to prepare RNIC.NLM to monitor your adapter pair.

The Redundant NIC NLM requires that several options be specified in order to create a pair. You can specify the options to RNIC.NLM when you load the nlm or on the command line after RNIC.NLM is loaded. To automate the commands on reboot, add them to your AUTOEXEC.NCF. See the examples in this chapter.

To complete the setup you need to know the following:

• The slot number assigned to each adapter. If the secondary adapter is not a PCI adapter then you need to know the hexidecimal value of the secondary adapter's I/O Port or Memory Mapped base IO address.

• If TCP/IP is bound to your adapter then you need to know your default router's IP address.

• Choose a name for your adapter pair.

  To set up a pair when you load the nlm use the following format:

  load rnic pair  -p  -s | -x
       [-r] [-backup]
  

  If RNIC is already loaded you can set up a pair by using the RNIC keyword on the system console. Its format is:

  rnic pair  -p -s|x -r
       [-backup]
  

  A description of each parameter follows:

  This parameter is required and identifies the Redundant NIC pair. The pairname must be 12 characters or less. It is case-sensitive. All ASCII characters are accepted.

  -P

  This parameter is required and tells the NLM the slot number of the IBM PCI Token-Ring Adapter that you want to be the active adapter initially.

  -S

  This parameter is required if the secondary adapter can be identified by a slot number. It tells the NLM the slot number of the IBM PCI Token-Ring Adapter that you want to be the backup adapter initially.

  -X

  This parameter is only needed when the -backup keyword is used and you cannot specify a slot for the secondary adapter. This parameter specifies the I/O port or the memory mapped address of the secondary adapter (in hex).

  -R

  This parameter is optional. It might be needed if you are using TCP/IP on your active adapter. If you do not load the Token-Ring_SNAP frame type then you do not need this parameter. If you load the Token-Ring_SNAP frame type then you only need this parameter if you have IP bound and you have a default IP router. If this parameter is not specified, IP will not know what the default router is after an adapter failover.

  -backup

  This parameter is optional. It should only be used if your backup adapter is not an IBM PCI Token-Ring adapter. If this parameter is used the primary adapter must load with the standby keyword.

Using Redundant NIC Software

The Command Line Interface

As stated previously, the RNIC command can be used on the system console after RNIC.NLM is loaded. This command can be used to view your pair, manually switch from active to backup, create a pair, destroy a pair, and change the mode.

rnic help

Type RNIC HELP and press ENTER to show the valid options for the rnic command. RNIC will also display this information.

rnic pair

The RNIC PAIR command is described in "Setting up a Redundant NIC Pair".

rnic unpair

RNIC UNPAIR will disassociate the backup adapter from the primary adapter. This command is necessary when you want to remove an existing pair.

rnic show

To determine the status of the RNIC NLM, enter RNIC SHOW. This will display the configured pair. If a pair is configured the following information will be displayed: the pair name and LAA (node address), the slots that the primary and secondary adapters are using, the switching mode of the pair (manual, automatic, or disabled), the current state of the primary adapter, the current state of the secondary adapter, the number of failovers that have occurred, and the time the last failover occurred.

Note: The terms primary and secondary do not refer to which adapter is currently active. The primary adapter is initially the active adapter and was configured by using the -p option on the command line. The secondary adapter is initially the backup adapter and was referred to by -s or -x on the command line.

rnic unpairall

To remove all pairs that are currently configured.

There are several states that each adapter can be in. The possible states are:

OPERATING

This adapter is open and operating.

STANDBY READY

This adapter is ready for failover if the active adapter fails.

CABLE DISCONNECTED

The cable was disconnected from this adapter while it was active.

ERROR DETECTED

There might be an adapter check error.

OPENING

The adapter is trying to open.

UNLOADED

One or more logical boards can no longer be located for this adapter.

rnic switch

rnic switch [ mode manual | mode auto | mode disabled ]

RNIC SWITCH will cause the pair identified by to failover from its active to its backup adapter when in auto or manual mode.

Normally the Redundant NIC pair will automatically failover from the active to the backup if a cable fault or adapter failure is detected. Use this command to change the mode of the pair so that an automatic failover will not occur. To prevent automatic failovers from occurring, set the pair to manual mode. In manual mode the rnic switch command is the only way to failover from the active to the backup adapter. Disabled mode will not allow failovers. You can use disabled mode when performing maintenance on the backup adapter.

Examples

1. AUTOEXEC.NCF of a simple Redundant NIC configuration after using INSTALL.NLM:

      set Time Zone = EST5EDT
      set Daylight Savings Time Offset = 1:00:00
      set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST  2:00:00 AM)
      set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST  2:00:00 AM)
      set Default Time Server Type = SINGLE
   
      # Note: The Time zone information mentioned above
      # should always precede the SERVER name.
      set Bindery Context = O=workgroup
      file server name NWSRV1
      ipx internal net 60990060
   
      # The network environment for this server consists
      # of a Token-Ring LAN with only one Frame Type
      load tcpip
      load odineb
   
      # Primary adapter
      LOAD IBMTRPO SLOT=3 NODE=400010203182 FRAME=TOKEN-RING NAME=IBMTRPO_1_TOK
      BIND IPX IBMTRPO_1_TOK NET=ABCD1
      # Secondary adapter loaded with the same frame type as the Primary
      LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY FRAME=TOKEN-RING
           NAME=IBMTRPO_2_TOK
   
      # Create the Redundant NIC pair with Primary slot=3, and Secondary Slot=2
      load rnic pair mypair -p3 -s2
   
      mount all
   

2. AUTOEXEC.NCF of a complex Redundant NIC configuration after using INSTALL.NLM:

      set Time Zone = EST5EDT
      set Daylight Savings Time Offset = 1:00:00
      set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST  2:00:00 AM)
      set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST  2:00:00 AM)
      set Default Time Server Type = SINGLE
   
      # Note: The Time zone information mentioned above
      # should always precede the SERVER name.
      set Bindery Context = O=workgroup
      file server name NWSRV1
      ipx internal net 60990060
   
      # The network environment for this server includes both Token-Ring frame
      # types, utilizes Source Routing, has an IP network with a default IP gateway,
      # and utilizes Route Switching via the IBM 8210
      LOAD IPXRTR routing=NLSP
      load tcpip
      load odineb
   
      # Primary Adapter
      LOAD IBMTRPO SLOT=3 NODE=400010203182 RTSWENABLE=YES FRAME=TOKEN-RING
           NAME=IBMTRPO_1_TOK
      BIND IPX IBMTRPO_1_TOK NET=ABCD1
      LOAD IBMTRPO SLOT=3 NODE=400010203182 RTSWENABLE=YES FRAME=TOKEN-RING_SNAP
           NAME=IBMTRPO_1_TSP
      BIND IPX IBMTRPO_1_TSP NET=FF1
      BIND IP IBMTRPO_1_TSP ADDR=10.20.31.82 MASK=ff.ff.ff.0 GATE=10.20.31.254
   
      # Secondary Adapter with the same frame types as Primary loaded, but no
      # bindings
      LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY RTSWENABLE=YES
           FRAME=TOKEN-RING  NAME=IBMTRPO_2_TOK
      LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY RTSWENABLE=YES
           FRAME=TOKEN-RING_SNAP  NAME=IBMTRPO_2_TSP
   
      # Create the Redundant NIC pair with the Primary slot=3, the Secondary
      # slot=2, and the Default IP gateway=10.20.31.254
      load rnic pair mypair -p3 -s2 -r10.20.31.254
   
      # If Source Routing is needed, then route.nlm must be loaded for
      # all the logical boards of both the primary and secondary adapter
      load route name=ibmtrpo_1_tok rsp=ar time=10
      load route name=ibmtrpo_1_tsp rsp=ar time=10
      load route name=ibmtrpo_2_tok rsp=ar time=10
      load route name=ibmtrpo_2_tsp rsp=ar time=10
   
      mount all
   

3. AUTOEXEC.NCF of installs with INETCFG (it is the same for both complex and simple installs):

      set Time Zone = EST5EDT
      set Daylight Savings Time Offset = 1:00:00
      set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST  2:00:00 AM)
      set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST  2:00:00 AM)
      set Default Time Server Type = SINGLE
      # Note: The Time zone information mentioned above
      # should always precede the SERVER name.
      set Bindery Context = O=workgroup
      file server name NWSRV2
      ipx internal net 35083DE8
   
      ; Network driver LOADs and BINDs are initiated via
      ; INITSYS.NCF. The actual LOAD and BIND commands
      ; are contained in INITSYS.NCF and NETINFO.CFG.
      ; These files are in SYS: ETC.
      load odineb
      sys:etc\initsys.ncf
      load rnic pair mypair -p7 -s6
   
      mount all
   

4. What is shown if user selects View All Commands from INETCFG after a simple installation:

      # The network environment for this server consists
      # of a Token-Ring LAN with only one Frame Type
      LOAD SNMP
      LOAD IBMTRPO NAME=TOK1_TOK FRAME=TOKEN-RING SLOT=7 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
      RTSWENABLE=NO
      LOAD IBMTRPO NAME=TOK2_TOK FRAME=TOKEN-RING SLOT=6 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES STANDBY
      RTSWENABLE=NO
      BIND IPX TOK1_TOK net=abcd1 seq=1
      LOAD DUMMY
      BIND DUMMY TOK2_TOK
   

5. What is shown if user selects View All Commands from INETCFG after a complex installation:

      # The network environment for this server includes both Token-Ring frame
      # types, utilizes Source Routing, has an IP network with a default IP gateway,
      # and utilizes Route Switching via the IBM 8210
      LOAD SNMP
      LOAD IBMTRPO NAME=TOK1_TOK FRAME=TOKEN-RING SLOT=7 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
      RTSWENABLE=YES RTSWTABLESIZE=1024
      LOAD IBMTRPO NAME=TOK1_TSP FRAME=TOKEN-RING_SNAP SLOT=7 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
      RTSWENABLE=YES RTSWTABLESIZE=1024
      LOAD IBMTRPO NAME=TOK2_TOK FRAME=TOKEN-RING SLOT=6 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES STANDBY
      RTSWENABLE=YES RTSWTABLESIZE=1024
      LOAD IBMTRPO NAME=TOK2_TSP FRAME=TOKEN-RING_SNAP SLOT=6 NODE=400010203181
           RXBUFFERS=32 TXBUFFERS=16 DATARATE=AUTO FULLDUPLEX=YES
      STANDBY RTSWENABLE=YES RTSWTABLESIZE=1024
      LOAD IPXRTR ROUTING=NLSP
      BIND IPX TOK1_TOK net=abcd1 seq=1
      BIND IPX TOK1_TSP net=ff1 seq=2
      LOAD ROUTE NAME=TOK1_TOK RSP=AR TIME=10
      LOAD ROUTE NAME=TOK1_TSP RSP=AR TIME=10
      LOAD ROUTE NAME=TOK2_TOK RSP=AR TIME=10
      LOAD ROUTE NAME=TOK2_TSP RSP=AR TIME=10
      LOAD Tcpip RIP=Yes Forward=No
      BIND IP TOK1_TSP ARP=Yes Mask=ff.ff.ff.0 Address=10.20.31.81
      LOAD DUMMY
      BIND DUMMY TOK2_TOK
      BIND DUMMY TOK2_TSP
   

6. AUTOEXEC.NCF of a simple Redundant NIC configuration after using INSTALL.NLM to configure two pairs (one using a non IBM PCI Token-Ring adapter as the secondary adapter):

      set Time Zone = EST5EDT
      set Daylight Savings Time Offset = 1:00:00
      set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
      set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
      set Default Time Server Type = SINGLE
   
      # Note: The Time zone information mentioned above
      # should always precede the SERVER name.
      set Bindery Context = O=workgroup
      file server name NWSRV1
      ipx internal net 60990060
   
      # The network environment for this server consists
      # of a Token-Ring LAN with only one Frame Type
      load tcpip
      load odineb
   
      # Primary adapter 1
      LOAD IBMTRPO SLOT=4 NODE=400000000004 DATARATE=M16 STANDBY FRAME=TOKEN-RING
           NAME=IBMTRPO_4_TOK
      BIND IPX IBMTRPO_4_TOK NET=1234
      #Secondary adapter 1 (notice this adapter is not an IBM PCI Token-Ring
           adapter)
      LOAD IBMMPCO SLOT=5 NODE=400000000004 DATARATE=16 ENABLEFDX FRAME=TOKEN-RING
           NAME=IBMMPCO_5_TOK
   
      # Primary adapter 2
      LOAD IBMTRPO SLOT=3 NODE=400010203182 FRAME=TOKEN-RING  NAME=IBMTRPO_1_TOK
      BIND IPX IBMTRPO_1_TOK NET=ABCD1
      # Secondary adapter loaded with the same frame type as the Primary 2
      LOAD IBMTRPO SLOT=2 NODE=400010203182 STANDBY FRAME=TOKEN-RING
           NAME=IBMTRPO_2_TOK
   
      # Create the Redundant NIC pair with Primary slot=4, and Secondary
      # Slot=5 (this pair uses the -backup parameter because the Secondary
      # adapter is not an IBM PCI Token-Ring adapter)
      load rnic pair bkpair -p4 -s5 -backup
      # Create the Redundant NIC pair with Primary slot=3, and Secondary Slot=2
      rnic pair mypair -p3 -s2
   
      mount all
   

Messages

Explanation: Your server is not able to allocate memory for RNIC.NLM

User Action: Try unloading NLM's that are not needed or add more memory to the server.

Explanation: The Redundant NIC NLM was unable to register for some NESL/NEB events. This could prevent the Redundant NIC pairs from functioning properly.

User Action: Update MSM.NLM to the latest available level.

Explanation: A Redundant NIC pair was created successfully and will be monitored for events from the adapters that make up the pair.

User Action: None.

Explanation: The Redundant NIC NLM must be told the slot for the primary and secondary adapters when a pair is created.

User Action: See "Setting up a Redundant NIC Pair" for information about creating a pair.

Explanation: Redundant NIC pairs must be given a name for the pairing to be completed.

User Action: Try to create the pair again and specify a pair name.

Explanation: You tried to use an existing pair name for another pair.

User Action: None.

Explanation: The default IP router address format that you specified was incorrect.

User Action: Verify the IP address of your router.

Explanation: There was a problem allocating memory. The server could be out of memory or there could be a problem with CLIB.NLM.

User Action: Try unloading NLM's that are not needed or add more memory to the server.

Explanation: There are no configured pairs to show at this time.

User Action: None.

Explanation: The adapter no longer appears to be where Redundant NIC thought it was. Pairs should get destroyed when the driver unloads. This message indicates that removing the pairs did not work.

User Action: Try removing the pair using RNIC UNPAIR . Recreate the pair.

Explanation: All Redundant NIC pairings were successfully removed.

User Action: None.

Explanation: The pairname specified with the RNIC switch command does not exist.

User Action: Use RNIC SHOW to determine the correct name.

Explanation: An RNIC switch command was issued to a Redundant NIC pair and the failover completed successfully.

User Action: None.

Explanation: The RNIC switch command that you specified was not correct.

User Action: Type RNIC HELP to get help with the rnic command.

Explanation: The Redundant NIC switch mode was successfully set to the specified mode.

User Action: None.

Explanation: The Redundant NIC pair was removed successfully.

User Action: None.

Explanation: You typed in a command that was not valid.

User Action: Type RNIC HELP to get help with the rnic command.

Explanation: The Redundant NIC pair was successfully refreshed.

User Action: None.

Explanation: The -s or the -sx parameter should be specified but not both.

User Action: Enter the rnic pair command again with either the -s or the -sx parameter.

Explanation: The pair will be completed when all logical boards that are needed are loaded.

User Action: Load the remaining logical boards that are needed to complete the pair.

Explanation: Your server is not able to allocate memory for RNIC.NLM.

User Action: Try unloading NLM's that are not needed or add more memory to the server.

Explanation: You typed an rnic pair parameter that was not valid.

User Action: Type RNIC HELP to get help with the rnic command.

Explanation: Your server is not able to allocate memory for RNIC.NLM.

User Action: Try unloading NLM's that are not needed or add more memory to the server.

Explanation: The initialization routine for the pair failed.

User Action: Try creating the pair again.

Explanation: There was a problem accessing the parameters structure.

User Action: Try setting up the pair again.

Explanation: The Redundant NIC NLM was not able to find any IBM Token-Ring boards loaded at this time.

User Action: Load Token-Ring boards for the primary and secondary adapters.

Explanation: There is no adapter in the slot that you specified as primary.

User Action: Specify the correct slot.

Explanation: Problem allocating memory. It is possible that the machine is low on RAM.

User Action: Try unloading NLM's that are not needed or add more memory to the server.

Explanation: The Config table for the adapter could not be read.

User Action: Make sure that you are using the correct LAN driver.

Explanation: Your LAN driver is too old.

User Action: Use the one that came with the RNIC.NLM diskette or a newer version if one is available.

Explanation: There is no adapter in the slot that you specified as secondary.

User Action: Specify the correct slot.

Explanation: The logical boards on the primary adapter do not match the logical boards on the secondary adapter.

User Action: Check the frame types for the primary and secondary adapters. They should match.

Explanation: The same Locally Administered Address must be assigned to each adapter using the NODE ADDRESS= command line keyword.

User Action: Set the Locally Administered Address on the primary and secondary adapters to the same address.

Explanation: There is a problem reading the adapter Config table.

User Action: Try setting up the pair again.

Explanation: The primary adapter must be open in order for Redundant NIC to initialize correctly.

User Action: Specify a primary adapter that is not shut down.

Explanation: The secondary adapter must be closed when Redundant NIC is being initialized.

User Action: Specify an adapter that was loaded with the standby keyword.

Explanation: Both adapters must be set to the same ring speed.

User Action: Configure the adapters so that they have the same ring speed.

Explanation: The secondary adapter did not respond to a request to shut down.

User Action: Try setting up the pair again.

Explanation: The primary adapter you specified is part of another Redundant NIC pair.

User Action: Specify a primary adapter that is not part of a Redundant NIC pair.

Explanation: The secondary adapter you specified is part of another Redundant NIC pair.

User Action: Specify a secondary adapter that is not part of a Redundant NIC pair.

Explanation: The primary adapter could not be reset.

User Action: Attempt to create the pair again.

Explanation: The pair that you tried to remove does not exist.

User Action: Type RNIC SHOW to find the correct pair name of the adapters that you would like to remove.

Explanation: There was a problem unpairing the adapters.

User Action: Try to remove the pair again.

Explanation: When the switching mode is disabled you cannot initiate a manual failover.

User Action: Set the switching mode to manual or auto.

Explanation: An attempt was made to failover to the backup adapter. The state of the backup adapter is preventing it from becoming an active adapter.

User Action: Make sure that the backup adapter is not open.

Explanation: The active adapter could not be shut down.

User Action: Try issuing a manual failover from the command line.

Explanation: The backup adapter could not be reset.

User Action: Try issuing a manual failover from the command line.